Packet tunnel management systems and methods

ABSTRACT

An Ethernet packet switch configured to manage one or more packet tunnels includes one or more ports; forwarding circuitry communicatively coupled to the one or more ports; and processing circuitry communicatively coupled to the forwarding circuitry, wherein the one or more packet tunnels are configured over the one or more ports, wherein each of the one or more packet tunnels has an associated maintenance endpoint (MEP), and wherein the processing circuitry is configured to manage the one or more packet tunnels based on performance characteristics determined through one or more of the associated MEP, intermediate switches, and a Network Management System.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present patent/application is a continuation of U.S. patentapplication Ser. No. 12/603,467 filed Oct. 21, 2009 and entitled“DEACTIVATING A PACKET TUNNEL BASED ON AT LEAST ONE PERFORMANCECHARACTERISTIC,” which is a divisional of U.S. patent application Ser.No. 11/963,719 filed Dec. 21, 2007 (now U.S. Pat. No.8,509,063 issuedAug. 13, 2013) and entitled “DEACTIVATING A PACKET TUNNEL BASED ON ATLEAST ONE PERFORMANCE CHARACTERISTIC,” the contents of which areincorporated by reference herein. This application is related tosimultaneously filed U.S. patent application Ser. No. 12/581,813 filedOct. 21, 2009 and entitled “MODIFYING A RATE BASED ON AT LEAST ONEPERFORMANCE CHARACTERISTIC” and naming Dackary Ronald Busch as inventor.

TECHNICAL FIELD

The present invention, in various embodiments, relates to deactivating apacket tunnel based on at least one performance characteristic.

BACKGROUND OF THE INVENTION

In some networks, a set of packet tunnels may be used to relay packetsfrom a first packet switch to a second packet switch. The set of tunnelsmay provide redundancy so that if one tunnel of the set fails, packetsmay still be relayed from the first packet switch to the second packetswitch using another tunnel of the set. Within the set of packettunnels, one tunnel may be activated and the other tunnels of the setmay be deactivated. The activated tunnel may remain active unless it isno longer able to relay packets from the first packet switch to thesecond packet switch.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the invention are described below withreference to the following accompanying drawings:

FIG. 1 is a schematic diagram of a network.

FIG. 2 is a schematic diagram of another network.

FIG. 2A is a schematic diagram of yet another network.

FIG. 3 is a block diagram of a packet switch.

FIG. 4 is another block diagram of a packet switch.

FIG. 5 is a schematic diagram of another network.

FIG. 6 is a chart illustrating performance characteristic data.

FIG. 7 is a chart illustrating other performance characteristic data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

According to one aspect of the invention, a network operating methodincludes providing a first packet switch configured to send a pluralityof packets from the first packet switch to a second packet switch via anetwork path traversing one or more intermediate packet switches.

The method also includes accessing data describing at least oneperformance characteristic of the network path and, based on the data,modifying a rate at which the first packet switch sends the plurality ofpackets to the second packet switch via the path. The method may furtherinclude notifying a network management system that is physicallydistinct from the first packet switch of the modified rate.

The accessing may include accessing using the first packet switch andthe modifying may include modifying using the first packet switch.Alternatively, the data may be received from a device other than thefirst packet switch. For example, the accessing may include receivingthe data from a network management system that is physically distinctfrom the first packet switch. Alternatively, the accessing may includereceiving the data from the second packet switch or receiving the datafrom one of the intermediate packet switches.

A first subset of the plurality of packets may include a first InternetProtocol (IP) destination address and a second subset of the pluralityof packets may include a second IP destination address. The first IPdestination address may be different than the second IP destinationaddress.

The network path may traverse a first one of the intermediate packetswitches comprising a first wireless transceiver and a second one of theintermediate packet switches comprising a second wireless transceiver.The method may further include connecting the first packet switch to thefirst one of the intermediate packet switches using first fiber orelectrically conductive cabling, connecting the first one of theintermediate packet switches to the second one of the intermediatepacket switches using a wireless link, and connecting the second one ofthe intermediate packet switches to the second packet switch usingsecond fiber or electrically conductive cabling.

According to another aspect of the invention, a network managementmethod includes receiving data describing at least one performancecharacteristic of a network path having a first endpoint on a firstpacket switch, and a second endpoint on a second packet switch. Thenetwork path traverses one or more intermediate packet switches. Themethod also includes, based on the received data, instructing the firstpacket switch to modify a rate at which the first packet switch sendspackets to the second packet switch via the network path.

The performance characteristic may include a frame loss value, a biterror rate value, a latency value, a jitter value, a bandwidth value, orother performance characteristic.

FIG. 1 illustrates a network 100 including five packet switches 102,104, 106, 108, and 110 and a network management system (NMS) 124. Anetwork path 120 has endpoints on packet switches 102 and 104 andtraverses packet switches 108 and 110. Another network path 122 hasendpoints on packet switches 102 and 106 and traverses packet switches108 and 110.

Packet switch 102 may send a packet to packet switch 104 via networkpath 120. In doing so, the packet may traverse packet switches 108 and110, which may be referred to as intermediate packet switches. Althoughnetwork path 120 has an endpoint on packet switch 104, packet switch 104might not be the final destination for the packet. Packet switch 104,after receiving the packet may forward the packet to another packetswitch or device (not illustrated).

Likewise, in some configurations, the packet might not be created bypacket switch 102 even though network path 120 has an endpoint on packetswitch 102. Instead, packet switch 102 might receive the packet fromanother packet switch or device (not illustrated). Accordingly, networkpath 120 may represent a portion of a path traveled by the packet fromthe packet's origin to the packet's destination.

While being forwarded from packet switch 102 to packet switch 104, thepacket may traverse a first communications link (not illustrated) thatfacilitates segment 112 of network path 120 and connects packet switch102 to packet switch 108. Similarly, the packet may traverse a secondcommunications link facilitating segment 114 of network path 120 andconnecting packet switch 108 to packet switch 110 and a thirdcommunications link facilitating segment 116 of network path 120 andconnecting packet switch 110 to packet switch 104.

Packet switch 102 may also send a packet to packet switch 106 vianetwork path 122. In doing so, the packet may traverse intermediatepacket switches 108 and 110. Like network path 120, network path 122 mayrepresent a portion of a path traveled by the packet from the packet'sorigin to the packet's destination.

Segment 112 of network path 122 may be facilitated by the firstcommunications link described above. In this configuration, the firstcommunications link may facilitate both network path 122 and networkpath 120. Alternatively, segment 112 of network path 122 may befacilitated by a fourth communications link connecting packet switch 102to packet switch 108. The fourth communications link might notfacilitate segment 112 of network path 120. Similarly, segment 114 ofnetwork path 122 may be facilitated by the second communications linkdescribed above or may alternatively be facilitated by a fifthcommunications link connecting packet switch 108 to packet switch 110.Segment 118 of network path 122 may be facilitated by a sixthcommunications link connecting packet switch 110 to packet switch 106.

The links described above may be fiber-optic cables, electricallyconductive cables, wireless links, or other links configured to relaypackets between packet switches. In one configuration, network paths 120and 122 may both be associated with a single Virtual Local Area Network(VLAN).

In sending packets to packet switch 104 via path 120, packet switch 102need not send packets belonging to only one Transmission ControlProtocol (TCP) session or packet all having a particular IP destinationaddress. Rather, packet switch 102 may send packets associated with aplurality of different TCP sessions and packets having a plurality ofdifferent IP destination addresses.

NMS 124 may be in communication with packet switches 102, 104, 106, 108,and 110. Although NMS 124 may be in communication with packet switches102, 104, 106, 108, and 110 as is illustrated logically in FIG. 1, NMS124 might not be physically connected to each of packet switches 102,104, 106, 108, and 110. In one configuration, NMS 124 may be physicallydistinct from the packet switches of network 100 and may be implementedas software executed by a computer.

NMS 124 may perform management functions for the packet switches ofnetwork 100. For example, NMS 124 may configure the packet switchesand/or receive alarm, configuration, and/or performance information fromthe packet switches. In some configurations, NMS 124 may enable a userto configure the packet switches.

Packet switch 102 includes a maintenance endpoint (MEP) 126. Inaddition, packet switch 104 includes a MEP 128. MEPs 126 and 128 maycommunicate with each other via path 120 to monitor connectivity betweenpacket switch 102 and packet switch 104. For example, MEP 126 may sendcontinuity check messages (CCMs) compliant with the Institute ofElectrical and Electronics Engineers (IEEE) 802.1ag standard. MEP 128may receive the CCMs from MEP 126 and take action if a particular periodof time expires without receiving a CCM from MEP 128. Similarly, MEP 128may send CCMs to MEP 126 and MEP 126 may monitor the CCMs received fromMEP 128 and take action if a particular period of time expires withoutreceiving an CCM from MEP 128.

Since network path 120 traverses several links and packet switches, arate at which packets may be forwarded from packet switch 102 to packetswitch 104, may be affected by the links and packet switchesfacilitating path 120. For example, packet switch 102 may forwardpackets to packet switch 108 via segment 112 of network path 120 at ahigh first rate but packet switch 108 may forward packets to packetswitch 110 via segment 114 of network path 120 as a low second rate. Inthis example, the overall rate at which packets may be forwarded frompacket switch 102 to packet switch 104 may be determined by the lowsecond rate of segment 114. Consequently, some packets sent at the highfirst rate from packet switch 102 to packet switch 108 may be discardedby packet switch 108.

In fact, the rates at which individual segments of network path 120 mayforward packets may vary over time. For example, if segment 114 ofnetwork path 120 is facilitated by a microwave radio link, the rate atwhich packets may be forwarded from packet switch 108 to packet switch110 via segment 114 may vary based on weather conditions. In anotherexample, the rate at which packets may be forwarded from packet switch110 to packet switch 104 via segment 116 of network path 120 may varybased on congestion in packet switch 110.

Accordingly, an overall rate at which packets may be forwarded frompacket switch 102 to packet switch 104 via network path 120 may varyover time. During some periods of time, some or all of the packets sentby packet switch 102 to packet switch 104 via network path 120 may bediscarded.

During these periods of time, packets may be discarded by packet switch108 or packet switch 110. In discarding packets, packet switch 108and/or packet switch 110 may use a method of discarding packets thatdiscriminates against the packets associated with network path 120 in anundesirable way. For example, packet switch 108 and/or packet switch 110may discard a large percentage or substantially all of the packetsassociated with network path 120 in order to favor higher prioritypackets. Doing so may drop a TCP session facilitated by packets relayedby network path 120 rather than allowing the TCP session to continue ata greatly reduced rate.

This undesirable discrimination may result if packet switch 108 and/orpacket switch 110 is relatively unsophisticated with respect to the wayit handles congestion. For example, packet switch 108 and/or packetswitch 110 may have an undesirable queue depth, an undesirable number ofqueues, or an undesirable method of servicing queues.

Accordingly, when the rate at which network path 120 is able to relaypackets changes, it may be desirable to adapt to the changed rate bycontrolling the number of packets sent by packet switch 102 via networkpath 120 rather than relying on packet switch 108 and/or packet switch110 to adapt the number of packets relayed by network path 120 to thechanged rate by discarding some of the packets transmitted by packetswitch 102. Controlling the number of packets sent by packet switch 102may be preferable if packet switch 102 has a more sophisticatedcongestion control capability than packet switch 108 and/or packetswitch 110. For example, managing congestion at packet switch 102 may bepreferable to managing congestion at packet switch 108 or packet switch110 if packet switch 102 is configured to implement weighted randomearly discard (WRED) and packet switches 108 and 110 are not.

Furthermore, even if packet switch 108 and/or packet switch 110 hascongestion control capability similar to packet switch 102, packetswitch 108 and/or packet switch 110 might not be configured in a desiredmanner. For example, if a first operator operates packet switches 102and 104 and a different second operator operates packets switches 108and 110, the second operator may not be willing to configure packetswitches 108 and 110 in a manner desired by the first operator.

Although the discussion above has focused on the effects that packetswitches 108 and 110 may have on a rate at which packets are forwardedvia path 120, other characteristics of the way that packets areforwarded from packet switch 102 to packet switch 104 (e.g., latency,jitter, packet loss, etc.) may additionally or alternatively be affectedby packet switches 108 and 110. These characteristics may also beinfluenced by controlling the rate at which packet switch 102 transmitspackets to packet switch 104 via path 120.

In one configuration, packet switch 102 may monitor or measure one ormore performance characteristics related to network path 120 to acquireperformance characteristic data. For example, packet switch 102 maydetermine a round-trip frame loss value, a round-trip bit error ratevalue, a round-trip latency value, a round-trip jitter value, abandwidth value, or other characteristic of network path 120 by sendingpackets (e.g., International Telecommunications Union-Telecommunications(ITU-T) Y.1731 Ethernet operations administration and maintenance (OAM)packets or connectivity fault management protocol data unit (CFMPDU)packets such as CFMPDU loopback packets) to packet switch 104 vianetwork path 120 and, in response, receiving packets from packet switch104.

As an alternative to measuring or determining performance characteristicdata of path 120 itself, packet switch 102 may receive the performancecharacteristic data from packet switch 104. For example, packet switch104 may determine a one-way latency value, one-way jitter value, anerrored frame seconds value, or a bandwidth value based on packetsreceived from packet switch 102. In one configuration, packet switch 104may determine the performance characteristic data based on ITU-T Y.1731Ethernet OAM packets or CFMPDU packets.

Once packet switch 104 has determined the performance characteristicdata, packet switch 104 may send the performance characteristic data topacket switch 102 (e.g., via one or more SNMP packets, one or more ITU-TY.1731 packets, or one or more CFMPDU packets). In anotherconfiguration, packet switch 104 may analyze the performancecharacteristic data of path 120 and instruct packet switch 102 to modifythe forwarding rate without providing the performance characteristicdata to packet switch 102. For example, packet switch 104 may instructpacket switch 102 to change a committed information rate (CIR) or excessinformation rate (EIR) associated with path 120 or may instruct packetswitch 102 to modify an ingress metering behavior and/or an egressshaping behavior of packet switch 102 as described below in relation toFIG. 4.

Similarly, packet switch 108 or packet switch 110 may determine theperformance characteristic data and provide the performancecharacteristic data to packet switch 102. For example, packet switch 108may provide the performance characteristic data to packet switch 102 ina type-length-value field of a link layer discovery protocol packetconforming to the IEEE 802.1AB standard. Alternatively, packet switch108 or packet switch 110 may determine the performance characteristicdata, analyze the performance characteristic data, and instruct packetswitch 102 to modify the forwarding rate without providing theperformance characteristic data itself to packet switch 102.

Similarly, NMS 124 may determine the performance characteristic data byaccessing performance characteristic data acquired by one or more ofpacket switches 102, 104, 108, and 110. NMS 124 may then provide theperformance characteristic data to packet switch 102, for example, viaone or more Simple Network Management Protocol (SNMP) messages, one ormore eXtensible Markup Language (XML) messages, a remote methodinvocation (RMI), or one or more NETCONF messages. Alternatively, NMS124 may determine the performance characteristic data, analyze theperformance characteristic data, and instruct packet switch 102 tomodify the forwarding rate without providing the performancecharacteristic data itself to packet switch 102.

After acquiring performance characteristic data of path 120, packetswitch 102 may determine that a forwarding rate at which packet switch102 forwards packets to packet switch 104 via path 120 should bemodified. For example, packet switch 102 may determine that thebandwidth of path 120 is less than the forwarding rate or that theround-trip latency of path 120 is excessive. Consequently, packet switch102 may determine that it should decrease the forwarding rate so thatthe forwarding rate is less than or equal to the bandwidth of path 120.Alternatively, packet switch 102 may determine that it should increasethe forwarding rate if the bandwidth of path 120 is greater than theforwarding rate.

Once packet switch 102 has determined that the forwarding rateassociated with path 120 should be modified (e.g., by using one of themethods described above), packet switch 102 may modify the forwardingrate. By way of example, packet switch 102 may modify the forwardingrate by modifying an ingress metering behavior and/or an egress shapingbehavior of packet switch 102 as described below in relation to FIG. 4.

In some configurations of network 100, packet switch 102 may notify NMS124 that packet switch 102 has changed the forwarding rate associatedwith path 120. In turn, NMS 124 may convey this information to a user.The information may be useful when a service level agreement (SLA) isassociated with path 120. For example, if an SLA specifies that networkpath 120 (or a portion thereof) is to have a particular CIR and packetswitch 102 modifies the forwarding rate so that the forwarding rate isless than the CIR, the user may be benefited by knowing that the SLA mayhave been violated as a result of packet switch 102 modifying theforwarding rate.

In one configuration of network 100, paths 120 and 122 may both beassociated with a particular VLAN identifier. In this configuration, ifpacket switch 102 modifies the forwarding rate associated with path 120,a forwarding rate associated with path 122 may be affected by themodification. For example, packet switch 102 might only be able tomodify a forwarding rate of substantially all packets associated withthe particular VLAN identifier rather than being able to modify aforwarding rate of some packets associated with the particular VLANidentifier but not modify a forwarding rate associated with otherpackets that are associated with the particular VLAN identifier.

According to another aspect of the invention, a first packet switchoperating method includes accessing data describing at least oneperformance characteristic of a packet tunnel. The packet tunnel isconfigured to relay packets from a first tunnel endpoint on the firstpacket switch to a second tunnel endpoint on a second packet switch viaone or more intermediate packet switches.

The accessing may include receiving a packet including the data from thesecond packet switch. The received packet may conform to the ITU-TY.1731 Ethernet OAM standard. The accessing may alternatively includereceiving a CFMPDU including the data from a MEP associated with thesecond packet switch. The CFMPDU may conform to the IEEE 802.1agstandard.

The accessed data may include data derived from the packets sent to thesecond tunnel endpoint via the tunnel. In some configurations, theaccessing may include receiving a packet that was not relayed by thetunnel, the received packet containing the data.

The method also includes, based on the data, modifying a rate at whichthe first packet switch forwards packets to the tunnel. The modifyingmay include modifying an egress shaping behavior of the first packetswitch and/or modifying an ingress metering behavior of the first packetswitch. The modifying may include increasing the rate or may includedecreasing the rate.

The method may further include forwarding the packets to the tunnel atthe modified rate. The forwarded packets may conform to the IEEE 802.1ahProvider Backbone Bridging standard.

The first packet switch may include a first MEP, the second packetswitch may include a second MEP, and the method may include sendingfirst IEEE 802.1ag CFMPDUs to the second MEP and receiving second IEEE802.1ag CFMPDUs from the second MEP.

The rate may be referred to as a first rate and the method may include,using the first packet switch, transmitting packets at the decreasedfirst rate to one of the intermediate packet switches via a linkconnecting the first packet switch to the one intermediate packet switcheven though the link is capable of relaying packets at a second ratethat is greater than the decreased first rate.

According to another aspect of the invention, a packet switch operatingmethod includes monitoring at least one performance characteristic of apacket tunnel. The packet switch is configured to receive packetsassociated with the packet tunnel. The packet switch may be anintermediate packet switch of the tunnel and the method may includereceiving packets associated with the tunnel and forwarding the receivedpackets only to another packet switch associated with the tunnel. Insome configurations, the packet switch may include an endpoint of thetunnel.

The method also includes determining, based on the monitoring, that datadescribing the monitored performance characteristic should be forwardedto a device configured to modify a rate at which packets ingress thepacket tunnel and sending the data to the device. The device may be anetwork management system configured to evaluate the data and instruct apacket switch on which the tunnel originates to modify the rate.

The method may include, prior to the sending, receiving first packetsassociated with the tunnel at a rate greater than the modified rate andsubsequent to the sending, receiving second packets associated with thetunnel at a rate less than or equal to the modified rate.

FIG. 2 illustrates a network 200. Network 200 includes packet switches102, 104, 108, and 110 described above in relation to FIG. 1, as well asNMS 124. In network 200, packet switch 102 is connected to packet switch104 via a packet tunnel 216. Segments 210, 212, and 214 may each befacilitated by a different link, such as a fiber-optic link,electrically conductive link, or wireless link, in a manner similar tothe way the links described above facilitate paths 120 and 122 ofnetwork 100.

Packet switch 102 includes a MEP 222 and packet switch 104 includes aMEP 224. MEPs 222 and 224 may be associated with tunnel 216 and maycommunicate with each other using CFMPDUs in order to monitorconnectivity between packet switches 102 and 104 in a manner similar tothat described above in relation to MEPs 126 and 128 of FIG. 1.

Tunnel 216 includes two tunnel endpoints 218 and 220. Endpoint 218 islocated on packet switch 102 and endpoint 220 is located on packetswitch 104. Tunnel 216 may relay packets from packet switch 102 topacket switch 104. In fact, in one configuration, tunnel 216 may relaypackets from packet switch 102 only to packet switch 104.

Packet switch 108 may receive packets associated with tunnel 216 frompacket switch 102 and may forward the received packets to packet switch110. In one configuration, packet switch 108 might not forward packetsassociated with tunnel 216 to a device other than packet switch 110.Similarly, packet switch 110 may receive packets associated with tunnel216 from packet switch 108, may forward the received packets to packetswitch 104, and might not forward the received packets to a device otherthan packet switch 104.

In some configurations, packets associated with tunnel 216 may includean identifier associated with the tunnel. For example, Ethernet packetsassociated with tunnel 216 may include a VLAN identifier having aparticular value. Packet switches 108, 110, and 104 may use theidentifier to associate packets with tunnel 216. In some configurations,packets associated with tunnel 216 may be encapsulated. For example, thepackets may be Ethernet packets encapsulated according to the IEEE802.1ah or IEEE 802.1Qay standards so that the packets have a backbonedestination address corresponding to packet switch 104.

Packet switch 102 may send packets to packet switch 104 via tunnel 216.Various performance characteristics may be associated with tunnel 216such as those performance characteristics described above (e.g.,bandwidth, latency, jitter, etc.). As with path 120 of FIG. 1, theforwarding performance of tunnel 216 may be limited by the forwardingperformance of a particular segment of tunnel 216. For example, abandwidth of segment 212 of tunnel 216 may be smaller than a bandwidthof segment 210 of tunnel 216 for various reasons described above such ascongestion, weather, etc.

Consequently, it may be beneficial to modify a forwarding rate at whichpacket switch 102 sends packets to tunnel 216 based on the bandwidth (orbased on another performance characteristic such as latency) of one ofthe segments of tunnel 216. One or more of the techniques describedabove in relation to FIG. 1 may be used to modify the forwarding rate.

For example, packet switch 102 may determine performance characteristicdata of tunnel 216 based on packets sent via tunnel 216 to packet switch104 (e.g., CFMPDUs sent to MEP 224). Alternatively or additionally,packet switch 102 may determine performance characteristic data oftunnel 216 based on packets, such as CFMPDUs sent by MEP 224, receivedvia tunnel 216 from packet switch 104 or, if tunnel 216 is auni-directional tunnel, packets received via a uni-directional tunnelcomplementary to tunnel 216. Based on the performance characteristicdata, packet switch 102 may modify the forwarding rate.

Alternatively, packet switch 102 may receive performance characteristicdata of tunnel 216 from packet switch 108, packet switch 110, packetswitch 104, and/or NMS 124 and based on the received performancecharacteristic data may modify the forwarding rate. In thisconfiguration, packet switch 102 may receive the performancecharacteristic data via a packet relayed by tunnel 216 (if tunnel 216 isbi-directional) or via a packet relayed outside of tunnel 216.

Alternatively, packet switches 102, 104, 108, and/or 110 may provideperformance characteristic data to NMS 124. NMS 124 may analyze theperformance characteristic data it receives and determine that theforwarding rate of packet switch 102 should be modified. NMS 124 maythen instruct packet switch 102 (e.g., via an SNMP message) to modifythe forwarding rate.

After either accessing the performance characteristic data itself orbeing instructed to modify the forwarding rate, packet switch 102 maymodify the forwarding rate (the rate at which packet switch 102 forwardspackets to tunnel 216). In one configuration, packet switch 102 maymodify the forwarding rate by modifying an egress shaping behaviorand/or an ingress metering behavior of packet switch 102.

By way of example illustrating the method of modifying the forwardingrate described above, packet switch 102 may receive informationindicating that segment 212 of tunnel 216 has the least amount ofbandwidth of the segments of tunnel 216 and that segment 212 iscurrently limited to 20 Mbps of bandwidth. Based on the information,packet switch 102 may determine that a bandwidth of tunnel 216 is also20 Mbps. Consequently, packet switch 102 may reduce the rate at which itsends packets to packet switch 104 via tunnel 216 to 20 Mbps. Packetswitch 102 may limit the rate in this manner even if segment 210 oftunnel 216 has an available bandwidth greater than 20 Mbps.

By reducing the forwarding rate, packet switch 102 may need to drop somepackets intended for tunnel 216 that it receives from other packetswitches (not illustrated) rather than forwarding the received packetsand relying on packet switch 108 to reduce the forwarding rate to matchthe 20 Mbps bandwidth of segment 212 of tunnel 216. Dropping packets atpacket switch 102 rather than packet switch 108 may be advantageous forthe reasons described above in relation to FIG. 1. For example, packetswitch 102 may use a desired congestion control method to drop thepackets and packet switch 108 may use an undesirable congestion controlmethod.

As a result of packet switch 102 reducing the forwarding rate to 20Mpbs, packet switch 108 may receive packets via tunnel 216 at a rate of20 Mbps and might not discard any of the received packets. Similarly,packet switches 110 and 104 may receive packets via tunnel 216 at a rateof 20 Mbps.

Continuing with the example, described above, packet switch 102 maysubsequently receive information indicating that the bandwidth ofsegment 212 of tunnel 216 has increased to 40 Mbps. Consequently, packetswitch 102 may increase the forwarding rate.

FIG. 2A illustrates a network 250. Network 250 includes packet switches102, 104, 108, and 110 described above in relation to FIGS. 1 and 2, aswell as NMS 124 and tunnel 216. In network 250, packet switch 108 isconnected to a network 252 rather than to packet switch 110. Network 252may facilitate tunnel 216 via one or more packet switches or otherdevices. Accordingly, tunnel 216 may relay packets from packet switch102 to packet switch 104.

Packet switches 102, 104, 108, and 110 and NMS 124 may be operated by afirst network operator and network 252 may be operated by a differentsecond network operator. Consequently, network 252 might not be incommunication with NMS 124. Accordingly, packet switch 102 might notreceive performance characteristic data of tunnel 216 from network 252.Despite this, packet switch 102 may still determine a bandwidth orlatency of a portion of tunnel 216 facilitated by network 252 based onperformance characteristic data provided by packet switch 110 or packetswitch 104.

If a forwarding performance of the portion of tunnel 216 facilitated bynetwork 252 limits the overall forwarding performance of tunnel 216,packet switch 102 may modify the rate at which it forwards packets totunnel 216 so that packets are dropped by packet switch 102 rather thana device or packet switch of network 252, which may have undesirable orunknown congestion control behavior.

According to another aspect of the invention, a packet switch includesforwarding circuitry configured to forward packets received by thepacket switch to a packet tunnel extending from the packet switch toanother packet switch via one or more intermediate packet switches. Thepacket switch also includes processing circuitry configured to accessdata describing at least one performance characteristic of the packettunnel and, based on the data, modify a rate at which the forwardingcircuitry forwards packets to the tunnel.

FIG. 3 illustrates a block diagram of packet switch 102. Packet switch102 may include processing circuitry 302, forwarding circuitry 304, andthree ports 306, 308, and 310. Of course, packet switch 102 may includeadditional ports. Three ports are illustrated for simplicity.

Processing circuitry 302 may access performance characteristic data anddetermine based on the data whether to modify a forwarding rate at whichforwarding circuitry 304 forwards packets to a network path such as path120 or a tunnel such as tunnel 216. If processing circuitry 302determines that the forwarding rate should be changed, processingcircuitry 302 may modify a configuration of forwarding circuitry 304 sothat forwarding circuitry 304 subsequently forwards packets to thenetwork path or tunnel at a modified rate.

In one configuration, processing circuitry 302 may be a processorexecuting programming stored by memory of packet switch 102. Otherimplementations of processing circuitry 302 are also possible.

Forwarding circuitry 304 forwards packets between ports 306, 308, and310. Port 310 may be associated with a network path or tunnel.Accordingly, forwarding circuitry 304 may receive packets on port 306that are intended for the network path or tunnel and may forward thereceived packets to port 310.

In one configuration, forwarding circuitry 304 may be an applicationspecific integrated circuit. Other configurations are also possible. Forexample, forwarding circuitry 304 may be a network processing unit.

FIG. 4 illustrates that forwarding circuitry 304 may include inputqueues 402, fabric 404, and output queues 406. Input queues 402 maytemporarily store a packet received on one of ports 306, 308, and 310until a destination port is determined for the packet. Once adestination port is determined, forwarding circuitry 304 may use fabric404 to relay the packet from input queues 402 to output queues 406.Output queues 406 may temporarily store a packet received from fabric404 until the packet can be transmitted out one of the ports.

Processing circuitry 302 may modify a rate at which forwarding circuitry304 forwards packets to a network path or tunnel by altering a meteringbehavior of input queues 402 so that input queues 402 are allowed tostore more or fewer of the packets intended for the network path ortunnel. Similarly, processing circuitry 302 may modify the forwardingrate by altering a shaping behavior of output queues 406. For example,if port 110 is associated with the network path or tunnel, processingcircuitry 302 may alter the shaping behavior of output queues 406 sothat more or fewer packets are sent to a destination packet switch, suchas packet switch 104, via the network path or tunnel. Altering themetering behavior of input queues 402 or the shaping behavior of outputqueues 406 may be accomplished using one or more of a number of knowntechniques (e.g., WRED).

Performance characteristic data of a packet tunnel may also be usefulwhen transitioning from a primary tunnel to a backup tunnel, or from abackup tunnel to a primary tunnel.

According to another aspect of the invention, a network includes a firstpacket switch, a second packet switch, an active primary tunnel couplingthe first packet switch to the second packet switch, and an inactivebackup tunnel coupling the first packet switch to the second packetswitch. The first packet switch is configured to forward packets to thesecond packet switch via the active primary tunnel, access datadescribing at least one performance characteristic of the primarytunnel, and, based on the data, deactivate the primary tunnel andactivate the backup tunnel.

FIG. 5 illustrates a network 500. Network 500 includes six packetswitches 502, 504, 506, 508, 510, and 512 and three packet tunnels 528,530, and 532. Network 500 also includes NMS 124, which was describedabove.

Tunnel 528 may have a first endpoint on packet switch 502 and a secondendpoint on packet switch 504 and may be relayed by intermediate packetswitches 506 and 508. Similarly, tunnels 530 and 532 may also have firstendpoints on packet switch 502 and second endpoints on packet switch 504and may be relayed by intermediate packet switches 508, 510, and 512.

In one configuration, packet switch 506 might not forward packetsassociated with tunnel 528 to a device other than packet switch 508.Similarly, packet switch 508 may receive packets associated with tunnel528 from packet switch 506, may forward the received packets to packetswitch 504, and might not forward the received packets to a device otherthan packet switch 504.

In some configurations, packets associated with tunnels 528, 530, and532 may include an identifier associated with the tunnel. For example,Ethernet packets associated with tunnel 528 may include a VLANidentifier having a particular value. Packet switches 504, 506, and 508may use the identifier to associate packets with tunnel 528. In someconfigurations, packets associated with tunnel 528 may be encapsulated.For example, the packets may be Ethernet packets encapsulated accordingto the IEEE 802.1ah or IEEE 802.1Qay standards so that the packets havea backbone destination address corresponding to packet switch 504.

Segment 514 of tunnel 528 may be facilitated by a communication linkconnecting packet switch 502 to packet switch 506 and segment 516 oftunnel 528 may be facilitated by a communication link connecting packetswitch 506 to packet switch 508. Segment 518 of tunnel 528 may befacilitated by a first communication link connecting packet switch 508to packet switch 504. This first communication link between packetswitch 508 and packet switch 504 may also facilitate segment 546 oftunnel 530. Alternatively, a second communication link connecting packetswitch 508 to packet switch 504 may facilitate segment 546 of tunnel530.

Segment 520 of tunnel 530 may be facilitated by a first communicationlink connecting packet switch 502 to packet switch 510. This firstcommunication link between packet switch 502 and packet switch 510 mayalso facilitate segment 544 of tunnel 532. Alternatively, a secondcommunication link connecting packet switch 502 to packet switch 510 mayfacilitate segment 544 of tunnel 532. Segment 522 of tunnel 530 may befacilitated by a communication link connecting packet switch 510 topacket switch 508.

Segment 524 of tunnel 532 may be facilitated by a communication linkconnecting packet switch 510 to packet switch 512. Segment 526 of tunnel532 may be facilitated by a communication link connecting packet switch512 to packet switch 504.

Packet switch 502 includes three MEPs 533, 536, and 540 and packetswitch 504 includes three MEPs 534, 538, and 542. MEPs 533 and 534 maybe associated with tunnel 528 and may communicate with each other usingCFMPDUs compliant with the IEEE 802.1ag standard in order to monitorconnectivity between packet switches 502 and 504 via tunnel 528 in amanner similar to that described above in relation to MEPs 126 and 128of FIG. 1. Similarly, MEPs 536 and 538 may monitor connectivity betweenpacket switches 502 and 504 via tunnel 530 and MEPs 540 and 542 maymonitor connectivity between packet switches 502 and 504 via tunnel 532.

Tunnels 528, 530, and 532 may have one or more characteristics. Each oftunnels 528, 530, and 532 may be active or inactive. If active, thetunnel may be configured to forward control packets (e.g., bridgeprotocol data units (BPDUs)) and non-control packets. In someconfigurations, a tunnel might not forward control packets when activebut instead may only forward non-control packets. If inactive, thetunnel may be configured to forward only control packets. In someconfigurations, packet switch 502 may prevent more than one of tunnels528, 530, and 532 from being simultaneously active.

Each of tunnels 528, 530, and 532 may be operational or non-operational.If operational, the tunnel may capable of relaying packets from oneendpoint of the tunnel to the other end of the tunnel. Ifnon-operational, the tunnel might not be capable of relaying packets.For example, if a link facilitating segment 514 of tunnel 528 is damagedor otherwise unable to relay packets from packet switch 502 to packetswitch 506, tunnel 528 may be non-operational.

Each of tunnels 528, 530, and 532 may be designated as primary orbackup. If primary, the tunnel may be configured to be initially activeand if backup, the tunnel may be initially inactive. Of course, aprimary tunnel could later become inactive and a backup tunnel couldlater become active. In some configurations, one tunnel of a set oftunnels may be designated as primary and other tunnels of the set may bedesignated as backup.

By way of example, in FIG. 5, tunnels 528, 530, and 532 may relaypackets from packet switch 502 to packet switch 504. Tunnel 528 may bedesignated as primary, may initially be active, and may be operational.Consequently, tunnel 528 may relay both control packets and non-controlpackets from packet switch 502 to packet switch 504.

Tunnels 530 and 532 may be designated as backup, may initially beinactive, and may be operational. Consequently, tunnels 530 and 532 mayrelay control packets (e.g., CFMPDUs used to monitor connectivity of thetunnels) from packet switch 502 to packet switch 504.

The active/inactive status of tunnels 528 and 530 may change if tunnel528 subsequently becomes non-operational (unable to relay packets). As aresult, tunnel 528 may have an inactive status. The status of tunnel 530may change from inactive to active, and tunnel 532 may remain inactive.Thereafter, tunnel 530 may relay control packets and non-control packetsand tunnel 532 may relay only control packets.

By way of another example, although tunnel 528 may initially be activeand tunnel 530 may initially be inactive, the status of tunnels 528 and530 may subsequently change if packet switch 502 accesses datadescribing at least one performance characteristic of tunnel 528 anddetermines that tunnel 530 has more favorable forwarding behavior thantunnel 528. In this example, packet switch 502 may deactivate tunnel 528and activate tunnel 530 to take advantage of the more favorableforwarding behavior of tunnel 530 even if tunnel 528 is stilloperational.

Packet switch 502 may consider a variety of data in determining thattunnel 530 is more favorable than tunnel 528. For example, packet switch502 may consider data describing more than one performancecharacteristic of tunnel 528 (e.g., bandwidth, jitter, latency, etc.)and may consider data describing the same performance characteristics oftunnels 530 and 532.

According to another aspect of the invention, a network operating methodincludes providing a first packet switch coupled to a second packetswitch via a primary packet tunnel having an active status and one ormore inactive backup packet tunnels having an inactive status.

A tunnel having an active status may constitute a tunnel configured toforward control packets and non-control packets from the first packetswitch to the second packet switch. A tunnel having an inactive statusmay constitute a tunnel configured to forward only control packets fromthe first packet switch to the second packet switch.

The method also includes accessing data describing at least oneperformance characteristic of the primary packet tunnel, and, based atleast on the data, deactivating the primary packet tunnel while stilloperational and activating one of the backup packet tunnels. The methodmay further include notifying a network management system that isphysically distinct from the first packet switch of the deactivating andthe activating.

The method may further include, subsequent to the accessing the firstand second data and based at least in part on the first and second data,determining that the one backup packet tunnel is able to forward packetsat a higher rate than the primary packet tunnel.

The data may be referred to as first data and the method may furtherinclude accessing second data describing performance characteristics ofthe one or more backup packet tunnels. The deactivating may includedeactivating based on the first data and the second data.

The performance characteristic may be a one-way frame loss value, aone-way bit error rate value, a one-way latency value, a one-way jittervalue, a round-trip frame loss value, a round-trip bit error rate value,a round-trip latency value, a round-trip jitter value, an errored frameseconds value, a bandwidth value, or other performance characteristic.

The accessing may include accessing using the first packet switch andthe deactivating may include deactivating using the first packet switch.Alternatively, the accessing may include accessing using a networkmanagement system and the method may further include, using the networkmanagement system, instructing the first packet switch to perform thedeactivating and the activating. The accessing may include receiving thedata from either the second packet switch or a network managementsystem.

According to another aspect of the invention, a network operating methodincludes providing a first device coupled to a second device via anactive primary packet tunnel and one or more inactive backup packettunnels. The primary packet tunnel may traverse one or more intermediatepacket switches, and the primary packet tunnel may include a firstendpoint associated with the first device and a second endpointassociated with the second device.

The method also includes accessing data describing performancecharacteristics of the one or more backup packet tunnels and, based atleast on the data, deactivating the primary packet tunnel and activatingone of the backup packet tunnels. The method may further includepreventing more than one tunnel selected from among the primary packettunnel and the one or more backup packet tunnels from beingsimultaneously active.

The method may further include, subsequent to the accessing andimmediately prior to the deactivating, sending a packet from the firstdevice to the second device via the primary packet tunnel and receivingthe packet from the primary packet tunnel at the second device.

According to another aspect of the invention, a first packet switchoperating method includes accessing data describing at least oneperformance characteristic of an active first packet tunnel. The activefirst packet tunnel is configured to relay packets from a first tunnelendpoint on the first packet switch to a second tunnel endpoint on asecond packet switch via one or more intermediate packet switches. Theaccessed data may include data derived from packets sent to the secondtunnel endpoint via the active first packet tunnel. In someconfigurations, the accessing may include receiving a packet that wasnot relayed by the first packet tunnel. The received packet may containthe data.

The method also includes, based at least on the data, deactivating thefirst packet tunnel and activating a second packet tunnel. The activatedsecond packet tunnel is configured to relay packets from the firstpacket switch to the second packet switch.

The method may further include, subsequent to the accessing, waiting auser-configurable amount of time before the deactivating of the firstpacket tunnel. The method may further include, prior to thedeactivating, preventing packets other than control packets and packetsconforming to the IEEE 802.1Qay provider backbone bridging trafficengineering (PBB-TE) standard from being forwarded to the active firstpacket tunnel.

The first packet switch may include a first MEP, the second packetswitch may include a second MEP, and the data may be derived from IEEE802.1ag CFMPDUs sent from the first MEP to the second MEP and/or fromIEEE 802.1ag CFMPDUs sent from the second MEP to the first MEP.

According to another aspect of the invention, a packet switch operatingmethod includes monitoring at least one performance characteristic of anactive first packet tunnel configured to forward packets from a firstdevice to a second device. The packet switch is configured to receivepackets associated with the first packet tunnel.

The method also includes determining, based on the monitoring, that datadescribing the monitored performance characteristic should be forwardedto the first device. The first device is configured to selectivelydeactivate the first packet tunnel and activate a second packet tunnelconfigured to forward packets from the first device to the seconddevice. The method also includes sending the data to the first device.

The packet switch may be an intermediate packet switch of the firstpacket tunnel and the method may further include receiving packetsassociated with the first packet tunnel and forwarding the receivedpackets only to another packet switch associated with the first packettunnel. Alternatively, the packet switch may be an endpoint of the firstpacket tunnel.

Returning now to FIG. 5, packet switch 502 may determine performancecharacteristic data of tunnel 528 based on packets sent via tunnel 528to packet switch 504 (e.g., CFMPDUs sent to MEP 534). Alternatively oradditionally, packet switch 502 may determine performance characteristicdata of tunnel 528 based on packets, such as CFMPDUs sent by MEP 534,received via tunnel 528 from packet switch 504 or, if tunnel 528 is auni-directional tunnel, packets received via a uni-directional tunnelcomplementary to tunnel 528. Packet switch 502 may similarly determineperformance characteristic data of tunnels 530 and 532.

The performance characteristic data may describe one or more performancecharacteristics of a tunnel. The performance characteristics may be theperformance characteristics described above (e.g., bandwidth, latency,jitter, frame loss, errored seconds, etc.).

Based on the performance characteristic data of tunnels 528, 530, and/or532, packet switch 502 may modify the status of tunnels 528, 530, and/or532. For example, tunnel 528 may be active and packet switch 502 maydetermine, based on performance characteristic data, that tunnel 530 isable to forward packets from packet switch 502 to packet switch 504 at ahigher rate than tunnel 528. Packet switch 502 may subsequentlydeactivate tunnel 528 (even though tunnel 528 may still be operational),activate tunnel 530, and leave tunnel 532 as inactive. Since tunnel 528may be operational prior to being deactivated and subsequent to beingdeactivated, packet switch 502 may forward packets to packet switch 504via tunnel 528 up until a point in time immediately prior todeactivating tunnel 528.

In some configurations, after determining that a currently inactivetunnel (e.g., tunnel 530) has more desirable forwarding characteristicsthan a tunnel that is currently active (e.g., tunnel 528), packet switch502 may wait a period of time prior to activating the currently inactivetunnel and deactivating the currently active tunnel to see if theforwarding characteristics of the currently active tunnel improve. Insome configurations, the duration of the period of time may be userconfigurable.

If the forwarding characteristics of the currently active tunnelimprove, packet switch 502 need not deactivate the currently activetunnel and activate the currently inactive tunnel. Waiting the period oftime may also ensure that the more desirable forwarding characteristicsof the currently inactive tunnel are sustained rather than beingtransitory.

Alternatively, packet switch 502 may receive performance characteristicdata of tunnels 528, 530, and/or 532 from packet switch 506, packetswitch 508, packet switch 510, packet switch 512, packet switch 504and/or NMS 124 and based on the received performance characteristic datamay modify the active/inactive status of two of tunnels 528, 530, and532. In this configuration, packet switch 502 may receive theperformance characteristic data via one or more packets relayed bytunnels 528, 530, and/or 532 or via a packet relayed outside of tunnel528, 530, and 532.

Alternatively, packet switches 506, 508, 510, 512, and/or 504 mayprovide performance characteristic data to NMS 124. NMS 124 may analyzethe performance characteristic data it receives and determine that theactive/inactive status of two of tunnels 528, 530, and 532 should bemodified. NMS 124 may then instruct packet switch 502 (e.g., via an SNMPmessage) to modify the active/inactive status of two of tunnels 528,530, and 532.

Packet switch 502 may notify NMS 124 when packet switch 502 has changedthe active/inactive status of any of tunnels 528, 530, or 532 so thatNMS 124 may keep track of the status of tunnels 528, 530, or 532 andinform a user of NMS 124 of the status of tunnels 528, 530, or 532.

FIG. 6 illustrates a chart 600 depicting performance characteristic datafor tunnels 528, 530, and 532 as of a first moment in time. As of thefirst moment in time, tunnel 530 may be designated as primary and mayhave an active status. Accordingly, tunnel 530 may be relayingnon-control packets from packet switch 502 to packet switch 504.

When compared to tunnel 528, tunnel 530 has a higher bandwidth but alsohas a larger latency and larger frame loss than tunnel 528. In someconfigurations, the fact that tunnel 528 has a better latency and frameloss than tunnel 530 may be enough to prompt packet switch 502 todeactivate tunnel 530 and activate tunnel 528 even though tunnel 528 hasa lower bandwidth. For example, if tunnel 530 is relaying voice over IPpackets that are very sensitive to latency and that require less than 20Mbps of bandwidth, tunnel 528 may be a better choice than tunnel 530.

In other configurations, bandwidth may be the dominant factor inselecting a tunnel. Packet switch 502 may be configured to select atunnel from among tunnels 528, 530, and 532 that has the highestbandwidth and that has latency and frame loss values that are below athreshold. For example, the threshold for latency may be 8 ms and thethreshold for frame loss may be 0.5%. In this example, packet switch 502may determine that tunnels 528, 530, and 532 all have acceptable latencyand frame loss values below the thresholds. Consequently, packet switch502 may select the tunnel having the greatest bandwidth from amongtunnels 528, 530, and 532, namely, tunnel 530.

Thus, packet switch 502 may select a tunnel based on more than oneperformance characteristic. As was described above, packet switch 502may access the performance characteristic data of chart 600 in manydifferent ways. For example, packet switch 502 may determine the dataitself, may receive the data from one or more of packet switches 504,506, 508, 510, and 512, or may receive the data from NMS 124.

FIG. 7 illustrates a chart 700 depicting performance characteristic datafor tunnels 528, 530, and 532 as of a second moment in time subsequentto the first moment in time. After accessing the data of chart 700,packet switch 502 may determine that tunnel 530 should no longer beactive because either tunnel 528 or tunnel 532 offers better forwardingperformance.

In a first example, packet switch 502 may deactivate tunnel 530 andactivate tunnel 532 since tunnel 532 offers greater bandwidth thantunnel 530. In a second example, packet switch 502 may deactivate tunnel530 and activate tunnel 528. In this example, packet switch 502 may havea latency threshold of 4 ms and may determine that tunnel 530 is nolonger acceptable due to its latency value of 6 ms and that tunnel 528is more attractive than tunnel 532 because tunnel 528 has a latencyvalue below the threshold. Packet switch 502 may make this determinationeven though tunnel 532 offers greater bandwidth than tunnel 528.

Accordingly, packet switch 502 may be configured to consider performancecharacteristic data in a variety of different ways in order to match atunnel's forwarding performance with a type of data to be forwarded.

Activating and deactivating tunnels based on performance characteristicdata may be beneficial when compared with known methods of activatingand deactivating tunnels based solely on a tunnel's operational status.When activating and deactivating based only on operational status,packet switch 502 might not deactivate tunnel 528 as long as MEPs 533and 534 indicate that tunnel 528 is operational (e.g., based on CFMPDUsexchanged by MEPs 533 and 534). However, even though tunnel 528 may beoperational, tunnel 530 or tunnel 532 may offer better forwardingperformance. Accordingly, using performance characteristic data todetermine which of a set of associated tunnels to activate may result inbetter network performance than relying solely on operational status ofthe associated tunnels.

According to another aspect of the invention, an article of manufactureincludes media including programming configured to cause processingcircuitry (e.g., a microprocessor) to perform processing that executesone or more of the methods described above. The programming may beembodied in a computer program product(s) or article(s) of manufacture,which can contain, store, or maintain programming, data, and/or digitalinformation for use by or in connection with an instruction executionsystem including processing circuitry. In some cases, the programmingmay be referred to as software, hardware, or firmware.

For example, the media may be electronic, magnetic, optical,electromagnetic, infrared, or semiconductor media. Some more specificexamples of articles of manufacture including media with programminginclude, but are not limited to, a portable magnetic computer diskette(such as a floppy diskette), hard drive, random access memory, read onlymemory, flash memory, cache memory, and/or other configurations capableof storing programming, data, or other digital information.

In compliance with the statute, the invention has been described inlanguage more or less specific as to structural and methodical features.It is to be understood, however, that the invention is not limited tothe specific features shown and described, since the means hereindisclosed comprise preferred forms of putting the invention into effect.The invention is, therefore, claimed in any of its forms ormodifications within the proper scope of the appended claimsappropriately interpreted in accordance with the doctrine ofequivalents.

What is claimed is:
 1. An Ethernet packet switch configured to manageone or more packet tunnels, the Ethernet packet switch comprising: oneor more ports; forwarding circuitry communicatively coupled to the oneor more ports; and processing circuitry communicatively coupled to theforwarding circuitry, wherein the one or more packet tunnels areconfigured over the one or more ports, wherein each of the one or morepacket tunnels has an associated maintenance endpoint (MEP), and whereinthe processing circuitry is configured to manage the one or more packettunnels based on performance characteristics determined through one ormore of the associated MEP, feedback from intermediate switches, and aNetwork Management System.
 2. The Ethernet packet switch of claim 1,wherein the processing circuitry is configured to manage by any ofactivation of a packet tunnel, deactivation of a packet tunnel, changeof a forwarding rate on a packet tunnel, modification of an egressshaping behavior on a packet tunnel, and modification of an ingressmetering behavior on a packet tunnel.
 3. The Ethernet packet switch ofclaim 1, wherein the processing circuitry, to manage the one or morepacket tunnels based on the performance characteristics, is configuredto modify a forwarding rate at which the forwarding circuitry forwardspackets to one of the one or more packet tunnels by one of altering ametering behavior of input queues and altering a shaping behavior ofoutput queues.
 4. The Ethernet packet switch of claim 1, wherein theforwarding circuitry is configured to send packets associated with aplurality of different Transmission Control Protocol sessions andpackets having a plurality of different Internet Protocol destinationaddresses over the one or more packet tunnels.
 5. The Ethernet packetswitch of claim 1, wherein each of the one or more packet tunnels isactive or inactive, wherein an active tunnel is configured to forwardcontrol packets and non-control packets and an inactive tunnel isconfigured to forward only control packets.
 6. The Ethernet packetswitch of claim 1, wherein the performance characteristics aredetermined through one of Ethernet operations, administration andmaintenance (OAM) packets and connectivity fault management protocoldata unit (CFMPDU) packets.
 7. The Ethernet packet switch of claim 1,wherein the one or more packet tunnels comprise a primary tunnel and anbackup tunnel, and wherein the processing circuitry is configured tomanage an active status and an inactive status of both of the primarytunnel and the backup tunnel.
 8. The Ethernet packet switch of claim 7,wherein processing circuitry is configured to manage the active statusand the inactive status of both of the primary tunnel and the backuptunnel based on latency and frame loss.
 9. The Ethernet packet switch ofclaim 7, wherein processing circuitry is configured to manage the activestatus and the inactive status of both of the primary tunnel and thebackup tunnel based on bandwidth.
 10. An Ethernet packet switch methodto manage one or more packet tunnels, the Ethernet packet methodcomprising: configuring one or more packet tunnels over one or moreports, wherein forwarding circuitry is communicatively coupled to theone or more ports, wherein processing circuitry is communicativelycoupled to the forwarding circuitry, and wherein each of the one or morepacket tunnels has an associated maintenance endpoint (MEP); determiningperformance characteristics associated with each of the one or morepacket tunnels through one or more of the associated MEP, feedback fromintermediate switches, and a Network Management System; and managingeach of the one or more packet tunnels, via the processing circuitry,based on associated performance characteristics.
 11. The Ethernet packetswitch method of claim 10, wherein them managing comprises any ofactivation of a packet tunnel, deactivation of a packet tunnel, changeof a forwarding rate on a packet tunnel, modification of an egressshaping behavior on a packet tunnel, and modification of an ingressmetering behavior on a packet tunnel.
 12. The Ethernet packet switchmethod of claim 10, wherein the managing comprises: modifying aforwarding rate at which the forwarding circuitry forwards packets toone of the one or more packet tunnels by one of altering a meteringbehavior of input queues or altering a shaping behavior of outputqueues, based on the performance characteristics.
 13. The Ethernetpacket switch method of claim 10, further comprising: sending, via theforwarding circuitry, packets associated with a plurality of differentTransmission Control Protocol sessions and packets having a plurality ofdifferent Internet Protocol destination addresses over the one or morepacket tunnels.
 14. The Ethernet packet switch method of claim 10,wherein each of the one or more packet tunnels is active or inactive,wherein an active tunnel is configured to forward control packets andnon-control packets and an inactive tunnel is configured to forward onlycontrol packets.
 15. The Ethernet packet switch method of claim 10,wherein the performance characteristics are determined through one ofEthernet operations, administration and maintenance (OAM) packets andconnectivity fault management protocol data unit (CFMPDU) packets. 16.The Ethernet packet switch method of claim 10, wherein the one or morepacket tunnels comprise a primary tunnel and an backup tunnel, andfurther comprising managing an active status and an inactive status ofboth of the primary tunnel and the backup tunnel.
 17. The Ethernetpacket switch method of claim 16, wherein the active status and theinactive status of both of the primary tunnel and the backup tunnel isbased on latency and frame loss.
 18. The Ethernet packet switch methodof claim 16, wherein the active status and the inactive status of bothof the primary tunnel and the backup tunnel is based on bandwidth. 19.An Ethernet network, comprising: a first switch; one or moreintermediate switches communicatively coupled to the first switch; asecond switch communicatively coupled to the one or more intermediateswitches; wherein one or more packet tunnels are configured between thefirst switch and the second switch, wherein each of the one or morepacket tunnels has an associated maintenance endpoint (MEP), and whereineach of the first switch and the second switch is configured to managethe one or more packet tunnels based on performance characteristicsdetermined through one or more of the associated MEP, feedback from theone or more intermediate switches, and a Network Management System. 20.The Ethernet network of claim 19, wherein the first switch and thesecond switch are configured to send packets associated with a pluralityof different Transmission Control Protocol sessions and packets having aplurality of different Internet Protocol destination addresses over theone or more packet tunnels.